-
Notifications
You must be signed in to change notification settings - Fork 312
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cluster: increase default timeout transfer leader in upgrade progress #1434
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1434 +/- ##
==========================================
+ Coverage 25.23% 33.59% +8.35%
==========================================
Files 264 225 -39
Lines 20743 17978 -2765
==========================================
+ Hits 5235 6039 +804
+ Misses 14705 10870 -3835
- Partials 803 1069 +266
Flags with carried forward coverage won't be shown. Click here to find out more.
Continue to review full report at Codecov.
|
[REVIEW NOTIFICATION] This pull request has been approved by:
To complete the pull request process, please ask the reviewers in the list to review by filling The full list of commands accepted by this bot can be found here. Reviewer can indicate their review by submitting an approval review. |
/merge |
This pull request has been accepted and is ready to merge. Commit hash: 52f03e6
|
What problem does this PR solve?
Close #1432
What is changed and how it works?
Increase default timeout of transfer leader from 300s to 600s during upgrade process. Note that user can always set another value as they wish with
--transfer-timeout
argument.Also implement
-s/--signal
argument support for systemd module, but not used for TiKV for now, as the necessary meta needed to validate TiKV versions are not available where it is called, and the change would be too large to be added into a patch release.Side effects
Related changes
Release notes: